Probable Cause:External temperature is too high; one or more fan failures; blockages that prevent fan air inflow/outflow.
Action to be Taken:Inspect chassis for any item that may be blocking chassis air flow. Verify adjacent equipment is not obstructing air flow. Verify that the fans are running via the CLI/Web Element Manager. Check air filters. Check the chassis maintenance schedule to see if chassis needs routine air filter replacement. Verify room temperature is within acceptable operating conditions.
Clear Condition: This condition is cleared when the card reaches its operating temperature range or is removed from the system.
Condition Clear Alarm:This condition is cleared by a starCardTempOK notification.
Action to be Taken:No action required. The cause for the card overheat condition should be investigated.
Important: This trap is obsolete.Action to be Taken: No action required. If the reboot was not scheduled, the admin logs can be examined to determine who invoked the reboot operation.
Probable Cause:Problem with incoming power; failure of power filters; hardware issue with card. Note that this is an extremely abnormal condition.
Action to be Taken:Verify that the power supplied to the chassis is operating correctly; use the CLI/Web Element Manager to check the state of the chassis power filters; replace the card.
Clear Condition:This is not a recoverable error except via restarting the card, so the condition is only cleared via a starCardUp or starCardActive notification.
Probable Cause:An operator has physically unlocked and removed a card from the chassis.
Action to be Taken:No action is required. If the card removal was unplanned, the admin logs can identify the time when the card was initially unlocked.
Probable Cause:The system logs should contain additional information about the cause of the boot failure.
Important: This trap is obsolete
Important: This trap is obsolete.
Important: This trap is obsolete.Probable Cause:A hardware failure on the redundancy crossbar card.
Probable Cause: A card was inserted into a slot which was configured for a different type of card. For example, a Gigabit Ethernet card was inserted into a slot configured for a Fast Ethernet card.
Clear Condition:A starCardUp or starCardActive notification is issued to confirm that this condition has been cleared.
Important: This object is obsolete.
Important: This trap is obsolete.Probable Cause:This is typically caused by an operator action; it can also represent the system recovering from a software or hardware fault.
Clear Condition:A starCardPACMigrateComplete notification is generated when the migration is complete.
Probable Cause:The packet processing card being migrated to was removed or reset before the migration completed; the migration operation was terminated by an operator; or a software or hardware failure on either packet processing card involved in the migration operation.
Clear Condition:The packet processing card in question will be reset; a starCardUp notification will be generated when the card is operational again.
Probable Cause:This is typically caused by an operator; it can also represent the system recovering from a software or hardware fault.
Action to be Taken:If the chassis management card switchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined.
Clear Condition:Verify the switchover completes successfully.
Clear Condition Alarm:A starCardSPCSwitchoverComplete is generated when the switchover operation has completed.
Action to be Taken:If the witchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined.
Probable Cause:The chassis management card being migrated to was removed or reset before the migration completed; the migration operation was terminated by an operator; or a software or hardware failure on either chassis management card.
Action to be Taken:Verify that both chassis management cards have the card locks in the locked position; examine the admin logs for the cause of the failure. If the cause was a software failure, the system crash logs should be examined.
Clear Condition:The chassis management card in question will be reset; a starCardUp notification will be generated when the card is operational again.
Probable Cause:A hardware failure on the fan tray. The fan tray should be replaced.
Action to be Taken:Verify there is no physical obstruction to the fans or replace the fan tray.
Clear Condition:Verify the fans are running
Condition Clear Alarm: A starFanInserted notification will be generated when the fan tray is replaced.
Action to be Taken:Replace the fan tray.
Clear Condition: Verify both fan trays are present and operational.
Condition Clear Alarm: A starFanInserted notification will be generated when the fan tray is replaced.
Important: This trap is obsolete.Probable Cause:For chassis management card CPUs this typically represents an abnormal amount of management (CLI, SNMP, CORBA) requests. For packet processing cards, this indicates that the system is reaching its capacity.
Action to be Taken:For chassis management cards, this may be a transient condition because of a burst of management activity. Monitor the CPU usage and if it is persistently high, examine the CPU table to determine which management activity is causing the excessive usage. For packet processing cards, this indicates the system is nearing its overall capacity. Monitor CPU usage and if it is persistently high, the system may need additional hardware to keep up with the system load.
Clear Condition:Verify that CPU usage returned to a normal load. This can represent a transient condition; the trap will be periodically repeated if the condition persists.
Probable Cause:For chassis management card CPUs this typically represents an abnormal number of management sessions, in particular CLI sessions. For packet processing cards this indicates that the system is reaching its capacity.
Action to be Taken: For chassis management cards, this may be a transient condition because of a burst of management activity. Monitor memory usage and if it is persistently high, examine the CPU table to determine which management activity is causing the excessive usage. Verify that large numbers of CLI sessions are not being generated and, if needed, terminate extra sessions. For packet processing cards, this indicated the system is nearing its overall capacity. Monitor memory usage and if it is persistently high, the system may need additional packet processing cards or additional card memory to keep up with the system load.
Clear Condition:Verify that memory usage has returned to a normal load. This can represent a transient condition; the trap will be periodically repeated if the condition persists.
Probable Cause: This indicates a hardware problem.
Action to be Taken: Replace the failing card.
Clear Condition: The card will be reset; a starCardUp will be generated if the card is restored to an operational state.
Probable Cause:This indicates a hardware problem.
Action to be Taken: Replace the failing card.
Clear Condition:The card will be reset; a starCardUp will be generated if the card is restored to an operational state.
Probable Cause:This could indicate an extremely busy CPU, a software problem, or a hardware issue.
Action to be Taken:Check the admin logs for an indication of the problem. Check the system crash logs for an indication of software problems. If the problem persists, replace the card.
Clear Condition:Verify that a chassis management card switchover or packet processing card migration completes successfully to recover from the failure condition.
Condition Clear Alarm:A starCardUp notification will be generated if the card is restored to an operational state.
Action To Be Taken: Reduce the total number of directly connected devices or clear ARP entries.
Important: This trap is obsoleteProbable Cause:The external power source has failed or has been disconnected, or a hardware failure on the PFU.
Action to be Taken:Verify that the input power to the power filter is operational and repair if needed. Verify that the connections to the power filter are intact and that the power filter is properly inserted into the chassis. Replace the power filter if required.
Clear Condition:Verify that both power filters are operating.
Condition Clear Alarm:A starPowerFilterAvail notification will be generated when the power filter is replaced.
Probable Cause:The power filter has been removed from the chassis, or no power is being provided to the PFU.
Action to be Taken: If the power filter removal wasn't planned, verify that the input power to the power filter is operational and repair if needed. Verify that the connections to the power filter are intact and that the power filter is properly inserted into the chassis. Replace the power filter if required.
Clear Condition:Verify that both power filters are operating.
Condition Clear Alarm:A starPowerFilterUnitAvail will be generated when the power filter is replaced.
Action to be Taken: No action required.
Probable Cause: Either a large number of SNMP notifications are being generated, or the configured threshold which limits the number of notifications is set too aggressively.
Actions to be Taken: Examine the admin logs and the SNMP trap logs to determine the source of the large number of traps and take appropriate actions; verify that the configured limit for the rate at which traps will be sent is appropriate for your environment.
Clear Condition Alarm:When the rate of SNMP notifications goes down, a starAlertsEnabled notification is generated.
Probable Cause:The AAA server is down, or there is a network issue preventing communication with the AAA server.
Actions to be Taken:Restore the AAA server to an operational status. Verify that the AAA server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems.
Clear Condition:Verify that communication to the AAA authentication server has been restored.
Condition Clear Alarm:When this condition clears, a starAAAAuthServerReachable notification will be generated. Note that if in a AAA group all the configured RADIUS servers are detected as down, their state is brought back to Active before the deadtime expiry period so that call setup signaling with AAA can proceed for subsequent requests. Therefore, when the last active authentication server in the group is detected as being down, a starAAAAuthServerUnreachable notification is generated. When the server state changes to Active, a starAAAAuthServerReachable notification is generated. This behavior is the same when there is only one RADIUS server configured.
Action to be Taken:No Action Required.
Action to be Taken:Examine the system configuration and correct the misconfiguration. See the user documentation for details on AAA configuration.
Clear Condition:Verify that communication to the AAA authentication server has been restored.
Condition Clear Alarm:When this condition clears, a starAAAAuthServerReachable notification will be generated.
Probable Cause:The AAA server is down, or there is a network issue preventing communication with the AAA server.
Actions to be Taken:Restore the AAA server to an operational status; Verify that the AAA server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems.
Clear Condition:Verify that communication to the AAA accounting server has been restored.
Condition Clear Alarm:When this condition clears a starAAAAccServerReachable notification will be generated. Note that if in a AAA group all the configured RADIUS servers are detected as down, their state is brought back to active before the deadtime expiry period so that call setup signaling with AAA can proceed for subsequent requests. Therefore, when the last Active Accounting server in the group is detected as being down, a starAAAAccServerUnreachable notification is generated. When the server state changes to Active, a starAAAAccServerReachable is generated. This behavior is the same when there is only one RADIUS server configured.
Action to be Taken:No Action Required.
Action to be Taken:Examine the system configuration and correct the misconfiguration. See the user documentation for details on AAA configuration.
Clear Condition:Verify that communication to the AAA authentication server has been restored.
Condition Clear Alarm:When this condition clears, a starAAAAccServerReachable notification will be generated.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken: If the PDSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the PDSN service is operational.
Condition Clear Alarm:A starPDSNServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of resources (packet processing cards) to support the running configuration.
Action to be Taken: If the PDSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the PDSN service is operational.
Condition Clear Alarm:A starHAServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken: If the FA service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the FA service is operational.
Condition Clear Alarm:A starFAServiceStart notification will be generated when the service is restarted.
Condition Clear Alarm:A starCLISessionEnd notification will be sent when the CLI session is terminated.
Probable Cause:Software error.
Actions to be Taken: Examine the admin logs for an indication of the source of the failure.
Clear Condition:Verify that a chassis management card switchover or card migration completes to recover from this condition.
Condition Clear Alarm: A starCardUp notification will be generated when the card restarts.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken: If the LAC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the LAC service is operational.
Condition Clear Alarm:A starLACServiceStart notification will be generated when the service restarts.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the LNS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the LNS service is operational.
Condition Clear Alarm:A starLNSServiceStart notification will be generated when the service restarts.
Probable Cause:The card was shut down by an operator; the card was removed by an operator; or a hardware or software fault caused the card to shut down. In the latter case an additional notification is generated with the specific failure.
Action to be Taken:If the card shutdown was not planned, verify that the card is present in the system and its card lock is in the locked position. Check the admin logs for the cause of the card shutdown.
Clear Condition:Verify that a chassis management card switchover/card migration completes to recover from the card shutdown.
Condition Clear Alarm:A starCardUp notification is generated when the card is restarted.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken: If the GGSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the GGSN service is operational.
Condition Clear Alarm:A starGGSNServiceStart notification will be generated when the service restarts.
Probable Cause: System usage has exceeded the capacity of the license installed, the license installed does not match the identification of the system. No license is installed.
Action to be Taken:Verify that the proper license is installed on the system, verify that the SPCs present in the system match those identified in the software license. If required, install an additional higher-capacity license.
clear condition:This condition is cleared when usage goes under the licensed limit.
condition clear alarm: This condition is cleared by a starLicenseUnderLimit notification.
Action to be Taken:Verify that the configured subscriber limit is correct. Configure additional services, or configure the existing service to permit a larger number of subscribers.
Probable Cause:The system has reached its maximum capacity based on the number of available packet processing cards/CPUs/memory.
Actions to be Taken: Examine the system CPU table to determine if there is abnormal system usage or if the system is reaching its capacity. If this condition persists, additional processing cards or memory may be required. Note that there is a configuration threshold which can be setup to monitor the number of NORESOURCE rejects.
Action to be Taken: No action is typically required. If an abnormal number of expiries occur, verify that the configuration expiry time is correct.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken: If the Closed RP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the Closed RP service is operational.
Condition Clear Alarm:A starClosedRPServiceStart notification will be generated when the service restarts.
Probable Cause:A software failure. The failing manager will be restarted.
Action to be Taken:Examine the admin and crash logs for more information about the failure.
Probable Cause: The remote EIS server is down or there is a network error making it unreachable.
Condition Clear Alarm: A starEISServerAlive notification will be generated when this condition is cleared.
Probable Cause:The remote CGF server is down or there is a network error making it unreachable.
Action to be Taken: Verify that the CGF server is functioning properly, or verify network connectivity to the CGF server.
Clear Condition:This condition is cleared when the CGF server becomes reachable.
Condition Clear Alarm: A starCgfServerAlive notification will be generated when this condition is cleared.
Probable Cause:The remote storage server is down. There is a network error making it unreachable.
Action to be Taken:Verify that the storage server is functioning properly, or verify network connectivity to the storage server.
Clear Condition:This condition is cleared when the storage server becomes reachable.
Condition Clear Alarm: A starStorageServerAlive notification is generated when this condition is cleared.
Probable Cause:This can happen if there is an inter-SGSN handoff and the new SGSN is not listed in GGSN service and its PLMN policy is set to reject unknown SGSNs.
Action to be Taken: List the SGSN address in the GGSN service.
Probable Cause:This is the result of an operator-configured congestion threshold being reached. This can be due to high usage of the resource being monitored which indicates that the system is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds.
Actions to be Taken: Verify that the congestion thresholds are correct, if the congested state is seem repeatedly, or, for sustained periods of time, additional system capacity may need to be brought online.
Clear Condition:This condition is cleared when the use of the specific resource falls below the configured limit.
Condition Clear Alarm: A starCongestionClear notification is sent when there are no congestion conditions for a service type.
Probable Cause: Multiple packet processing cards are no longer available due to failure, removal, or other operator action; or, configuration changes have been made which eliminated the availability of redundant cards.
Action to be Taken:Bring additional packet processing cards online to match the number of configured cards, or update the configuration to require fewer active cards.
Clear Condition:This condition is cleared when the number of active packet processing cards reaches or exceeds the configured number.
Probable Cause: Multiple line cards (LCs) are no longer available due to failure, removal, or operator action.
Action to be Taken:Bring additional LCs online to match the number of configured cards, or update the configuration to require fewer active LCs.
Clear Condition:This condition is cleared when the number of active line cards reaches or exceeds the configured number.
Probable Cause: Both SPIOs are no longer available due to failure, removal, or operator action.
Action to be Taken: Bring at least one SPIO online.
Clear Condition: This condition is cleared when a SPIO is made active.
Probable Cause:IP Pool Sharing Protocol (IPSP) is running between two HAs (a primary and a secondary). The primary HA has now released the last address that was in use. This presumably is done in preparation for taking the primary HA out of server.
Action to be Taken:Perform the desired maintenance on the primary HA that required taking the device out of service.
Probable Cause: The PCF has failed or is otherwise unavailable, or a network connectivity problem makes it unreachable.
Action to be Taken:If the PCF outage was unplanned, restart/reset the PCF, and verify network connectivity.
Probable Cause: The remote DHCP server is down or there is a network error making it unreachable.
Action to be Taken:Verify that the DHCP server is functioning properly; verify network connectivity to the DHCP server.
Clear Condition:The condition is cleared when the DHCP server becomes reachable, or if the configuration is changed to not use this server.
Condition Clear Alarm:A starDhcpAlive notification is generated when the server becomes reachable.
Probable Cause:The NTP server is down or unavailable, or there is a network connectivity issue that prevents access to the NTP server.
Action to be Taken:Verify that the NTP server is running properly; verify that the connection to the NTP server is functioning.
Clear Condition:This condition is cleared when the NTP server becomes reachable.
Condition Clear Alarm:This condition is cleared by a starNTPPeerReachable notification.
Probable Cause:All configured NTP servers are no longer available, or some/all NTP servers have been un-configured by an operator.
Action to be Taken:Verify that the NTP server(s) are running properly and that the network connections to the NTP servers are available. Check the configured of the NTP servers for correctness. If needed, configure additional NTP servers.
Clear Condition: This condition is cleared when any (one) NTP server becomes reachable.
Condition Clear Alarm:This condition is cleared by a starNTPSyncEstablished notification.
Probable Cause:Misconfiguration of the peer router address or inability to route to the peer.
Action to be Taken: Verify the peer address is correct; verify that the peer is operational; verify network connectivity to the peer.
Probable Cause:The remote server is down or there is a network error making it unreachable. A starNwReachServerAlive notification will be generated when this condition is cleared.
Probable Cause: GTPP storage server has purged un-acked GCDRs after hitting the max allowed configured limit on un-acked GCDR in the backup database.
Action to be Taken: Check for the unacked file generated for these GCDRs.
Clear Condition: There is no clear condition for this notification.
Condition Clear Alarm: There is no clear alarm for this notification.
Probable Cause:GTPP storage server has generated and saved all the unacked GCDRs to file.
Action to be Taken:Operator needs to FTP the generated file.
Clear Condition:There is no clear condition for this notification.
Condition Clear Alarm:There is no clear alarm for this notification.
Probable Cause:The NTP server is reachable. This could indicate a newly configured NTP server (including an initial configuration on system startup) or could indicate a previously unreachable server has become reachable.
Action to be Taken:No action required.
Probable Cause:An NTP server is available when previously no server was available. This could indicate a newly configured NTP server (including an initial configuration on system startup) or could indicate that one or more previously unreachable server(s) has become reachable.
Action to be Taken:No action required.
Action to be Taken:No action required.
Action to be Taken:No action required.
Action to be Taken:No action required.
Action to be Taken:No action required.
Action to be Taken:No action required.
Action to be Taken:No action required.
Action to be Taken:Operator has to configure with matching prefix if required.
Action to be Taken:No action required.
Action to be Taken:No action required.
Probable Cause:The BGP peer is not-operational; the network between the chassis and the BGP peer is experiencing an outage; or LC failure(s) on the chassis.
Action to be Taken:Verify the BGP peer is operational; verify network connectivity to the BGP peer.
Clear Condition Alarm:A starBGPPeerSessionUp notification is generated when connectivity is reestablished.
Action to be Taken:No action is required.
Action to be Taken:No action is required.
Action to be Taken:No action is required.
Action to be Taken:Verify that the BGP Peer is running and is properly configured. Verify the network link to the BGP Peer.
Clear Condition:This condition is cleared when communication with the BGP peer is reestablished.
Condition Clear Alarm: This condition is cleared by a starBGPPeerReachable notification.
Action to be Taken: No action required.
Action to be Taken:Verify the state of the configured AAA server(s) and restart them if required. Verify the network link to the AAA Server(s). Configure additional AAA servers if required.
Clear Condition:This condition is cleared when communication with any single AAA service is (re)established.
Condition Clear Alarm:This condition is cleared by a starSRPAAAReachable notification.
Action to be Taken: Verify that the switchover was a planned operator action.
Action to be Taken: Verify the communication path to the standby HA.
Action to be Taken:Update the configuration of the standby HA to match the active HA.
Clear Condition:This condition is cleared when the active HA confirms that the standby HA has a configuration.
Condition Clear Alarm:This condition is cleared by a starSRPConfigInSync notification.
Action to be Taken: No action required.
Action to be Taken:If this condition persists, the identified card needs to be replaced.
Action to be Taken:No action required.
Action to be Taken: Operator has to check the reason for the unavailability of the server and act accordingly.
Action to be Taken:Increase the value of fmd-max-call-rate or set no fmd-max-call-rate.
Condition Clear Alarm:This condition is cleared by a starFMDCallRateUnderControl notification
Action to be Taken:No action required.
Probable Cause:The amount of information being sent to the storage server is approaching the server's capacity, the storage server has other tasks running on it which are taking CPU time, a problem with the Storage Server is causing the CPU to be abnormally busy.
Condition Clear Alarm: This condition is cleared by a starStorageServerCPUNormal notification.
Probable Cause:This can be caused by an improper configuration, or by the failure or removal of other cards in the system.
Condition Clear Alarm: This condition is cleared by a starStorageServerDiskSpaceOK notification.
Probable Cause: This can be caused by an improper configuration, or by the failure or removal of other cards in the system.
Action to be Taken:Install or configure additional redundant cards.
Condition Clear Alarm:A starCardSPOFClear notification will be generated is a redundant card becomes available. Notifications like starCardDown could also obsolete this notification.
Probable Cause:No action has been taken long for the GCDR files generated by Storage Server.
Condition Clear Alarm:This condition is cleared by a starStorageServerOldGcdrCleared notification.
Probable Cause: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken:If the IPSG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the IPSG service is operational.
Condition Clear Alarm:A starIPSGServiceStart notification will be generated when the service is restarted.
Condition Clear Alarm: A starHAReachable notification will be generated when the HA becomes reachable.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken:If the ASNGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Condition Clear Alarm:A starASNGWServiceStart notification will be generated when the service is restarted.
Probable Cause:Software error.
Actions to be Taken: Examine the admin logs for an indication of the source of the failure.
Clear Condition:Verify that the task has been restarted.
Condition Clear Alarm: A starTaskRestart notification will be generated when task has successfully restarted.
Actions to be Taken: None.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken: If the CSCF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the CSCF service is operational.
Condition Clear Alarm:A starCSCFServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken: If the DHCP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the DHCP service is operational.
Condition Clear Alarm:A starDHCPServiceStart notification will be generated when the service is restarted.
Action to be Taken: If no OPTCMDB file is found in the specified directory, then place an OPTCMDB-FULL file in the directory and give an upgrade command. If the error is related to a merge/loading failure then give an upgrade command with a new inc/full database file.
Condition Clear Alarm:This condition is cleared by a starContFiltDBErrorClear notification.
Action to be Taken:No action required.
Action to be Taken:If there is no or there is an invalid OPTBLDB file in the specified directory then place a OPTBLDB_FULL file in the directory and give an upgrade command.
Condition Clear Alarm: This condition is cleared by a starBLDBErrorClear notification.
Action to be Taken:Place a valid OPTCMDB-FULL file or OPTCMDB_INCR file in the directory and give an upgrade command.
Condition Clear Alarm:This condition is cleared by a starContFiltDBUpgradeErrorClear notification.
Action to be Taken:No action required.
Action to be Taken: No action required
Condition Clear Alarm:This condition is cleared by a starBLDBUpgradeErrorClear notification.
Action to be Taken: No action required.
Action to be Taken:No action required.
Probable Cause:This is the result of an operator-configured congestion overload value reached. This notification indicated a chassis-wide overload condition, typically overall system usage reaching some fraction of capacity. Once this limit is reached, the configured behavior is taken. This will cause certain older and/or dormant calls to be dropped in favor of newer calls. Note that this is similar to, but different from, the starCongestion notification. Typically the 'overload' condition will be configured to trigger at an earlier point.
Actions to be Taken: Verify that the congestion overload thresholds are correct; if the congested state is seen repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
Clear Condition:This system is cleared when the use of the specific resource falls below the configured limit.
Condition Clear Alarm: A starOverloadSystemClear notification is sent when the system overload condition is clear.
Probable Cause: This is the result of an operator-configured congestion overload value reached. This notification indicated a service-specific overload condition, typically the use of the service reaching some fraction of capacity. Once this limit is reached, the configured behavior is taken. This will cause certain older and/or dormant calls to be dropped in favor of newer calls. Note that this is similar to, but different than, the starCongestion notification. Typically the 'overload' condition will be configured to trigger at an earlier point. Since this is a service-specific notification, it is possible to receive multiple notifications for different services.
Action to be Taken:Verify that the congestion overload thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
Clear Condition:This system is cleared when the use of the specific resource falls below the configured limit.
Condition Clear Alarm:A starOverloadServiceClear notification is sent when the service-specific overload condition is clear.
Probable Cause:GTPP Storage Server cluster hardware/software component failure, or maintenance of GTPP Storage Server is in progress.
Probable Cause:GTPP storage server cluster hardware/software component failure or maintenance of GTPP storage server is in progress.
Probable Cause:Fiber-optic cable may have been damaged or pulled out or disk fault may have been occurred.
Condition Clear Alarm:This condition is cleared by a starStorageServerClusPathOK notification.
Probable Cause:Interconnect interface may have been failed, or interconnect interface cable may have been pulled out.
Condition Clear Alarm:This condition is cleared by a starStorageServerClusInterCOK notification.
Probable Cause: Interface may have been failed, interface cable may have been pulled out.
Condition Clear Alarm:This condition is cleared by a starStorageServerClusIntfOK notification.
Probable Cause:The amount of free memory used by storage server is approaching the server's capacity.
Condition Clear Alarm:This condition is cleared by a starStorageServerMemNormal notification.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (packet processing cards) to support the running configuration.
Action to be Taken:If the shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running on the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the PDIF Service is operational.
Condition Clear Alarm:A starPDIFServiceStart notification will be generated when the service is restarted.
Probable Cause: This is typically caused by session manager task fails and successfully completed recovery.
Action to be Taken:No action required.
Problem Cause: The Diameter peer has failed, or a network connectivity problem prevents reaching the peer.
Condition Clear Alarm:A starDiameterPeerUp notification will be generated when the peer is up.
Problem Cause: The Diameter server has failed, or a network connectivity issue prevents reaching the server.
Condition Clear Alarm:A starDiameterServerReachable notification will be generated when the server is reachable.
Probable Cause:CDR files are not being moved off the system, or these files are not being deleted after they have been transferred.
Probable Cause: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the SGSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the SGSN service is operational.
Condition Clear Alarm:A starSGSNServiceStart notification will be generated when the service is restarted.
Probable Cause: Received destination unavailable (DUNA) message, or SCTP association is down, or remote peer server is down.
Action to be taken:Verify that the peer server is up.
Probable Cause: Received a destination available (DAVA) message. SCTP Association is up. Remote peer server is up.
A starM3UAPCAvailable message is generated only after a starM3UAPCUnavailable message was generated.
Probable Cause: This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCPUUtilization notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCPUMemory notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearLicense notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearSubscriberTotal notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearSubscriberActive notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortRxUtil notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortTxUtil notification will be generated when the measured value falls below the threshold.
Probable Cause: This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortHighActivity notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAuthFail notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAuthFailRate notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user -configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAcctFail notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAcctFailRate notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAARetryRate notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCallSetup notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCallSetupFailure notification will be generated when the measured value falls below the threshold.
Probable Cause: This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCallRejectNoResource notification will be generated when the measured value falls below the threshold.
Probable Cause: This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in an alarm mode, a starThreshClearPacketsFilteredDropped notification will be generated when the measured value falls below the threshold.
Probable Cause: This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPacketsForwarded notification will be generated when the measured value falls below the threshold.
Probable Cause: This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearSessCPUThroughput notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPPoolAvail notification will be generated when the measured value falls below the threshold.
The percentage IP pool addresses in HOLD state in a context has gone above the configured threshold.
The percentage IP pool addresses in USED state in a context has gone above the configured threshold.
The percentage IP pool addresses in HOLD state in a context has gone below the configured threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortSpecRxUtil notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortSpecTxUtil notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in 'alarm' mode, a starThreshClearHACallSetupRate notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcCallSetupRate notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcRegReplyError notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcReregReplyError notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcDeregReplyError notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearFASvcRegReplyError notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNCallSetupRate notification is generated when the measured value falls below the threshold.
Probable Cause: This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNSvcCallSetupRate notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNSvcA11RRPFailure notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode a starThreshClearPDSNSvcA11RRQMsgDiscard notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode a starThreshClearPDSNSvcA11RACMsgDiscard notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNSvcA11PPPSendDiscard notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAMgrQueue is generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm: If the thresholding subsystem is configured to run in an alarm mode, a starThreshClearIPSECIKERequests notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECIKEFailures notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECIKEFailRate notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECTunSetup notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECTunEstabl notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold. Reject Call Requests indicate that an IPSEC Manager has reached its maximum allowable number of IPSEC tunnels.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECTunnelsTotal notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCSCFSvcRouteFailure notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearContFiltRating notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearContFiltBlock notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in an alarm mode, a starThreshClearCDRFileSpaceOverLimit notification is generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearEDRFileSpaceOverLimit notification generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDIFCurrSess notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearPDIFCurrActSess notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold. This threshold potentially indicates an overload condition due which prevents processing CDR messages at the same rate as the incoming packets.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearCDRFlowControl notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearASNGWSessTimeout notification is generated when the value falls below the threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshASNGWSessSetupTimeout notification is generated when the value falls below the threshold.
Probable Cause:This is a-user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearASNGWAuthFail notification is generated when the value falls below the threshold.
Important: This object is obsolete.Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshASNGWR6InvNai notification is generated when the value falls below the threshold.
Important: This object is obsolete.Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearASNGWMaxEAPRetry notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshASNGWNWEntryDenial notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshASNGWHandoffDenial notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearSGSNSessions notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearPerServiceSGSNSessions notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearSGSNPdpSessions notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearPerServiceSGSNPdpSessions notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearFWDoSAttack notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearFWDropPacket notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearFWDenyRule notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If thresholding is configured to run in alarm mode, a starThreshClearFWDenyRule notification is generated when the value falls below the threshold.
Probable Cause: This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause: This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:A starThreshClearASNGWSessions notification is generated when the value falls below the threshold.
Possible Cause:This is a user-configurable threshold.
Condition Clear Alarm:A starThreshClearPerServiceASNGWSessions notification is generated when the value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause: This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm model, a starThreshClearFNGCurrSess notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearFNGCurrActiveSess notification will be generated when the measured value falls below the threshold.
Probable Cause: This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause: This is a user-configurable threshold.
Probable Cause:This is a user configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearNAPTPortChunks notification will be generated when the measured value exceeds the threshold.
Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDGCurrSess notification will be generated when the measured value falls below the threshold.
The chassis-wide count of current PDG active sessions has gone above the configured threshold value.
Probable Cause: This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDGCurrActiveSess notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearNAPTPortChunks notification will be generated when the measured value exceeds the threshold.
Probable Cause:This is a user-configurable threshold.
The per-service CSCF Total Active Registrations count has gone above the configured threshold value.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user configurable threshold.
Probable Cause:This is a user-configurable threshold.
The Per-Service CSCF Presence failure count has gone above the configured threshold. Probable Cause:This is a user-configurable threshold.
The Per-Service CSCF Reg-Auth failure count has gone above the configured threshold. Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearBGPRoutes notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearTpoRtoTimeout notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearTpoDnsFailure notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold. If the thresholding subsystem is configured to run in alarm mode, a starThreshClearTpoLowCompressionGain notification will be generated when the measured value falls below the threshold.
Probable Cause: This is a user-configurable threshold
Probable Cause:This is a user-configurable threshold. Possible reasons for this alarm:
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCardTemperaturePowerOffLimit notification will be generated when the measured temperature falls, making the distance between the poweroff/reset point and current temperature larger than the set threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAcctArchiveQueue-1 notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAcctArchiveQueue-2 notification will be generated when the measured value falls below the threshold.
Probable Cause:This is a user-configurable threshold.
Condition Clear Alarm:If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAcctArchiveQueue-3 notification will be generated when the measured value falls below the threshold.
Condition Clear Alarm:A starOSPFNeighborFull notification will be generated when the neighbor is restored.
Probable Cause:All related Peer Server Processes(PSPs) are in the ASP-Down state for this peer server.
Condition Clear Alarm:A starM3UAPSActive notification will be generated when the peer server becomes reachable as at least one PSP is in ASP-Active state.
Probable Cause:SCTP association is down or remote peer server is down.
Condition Clear Alarm:A starM3UAPSPUp notification will be generated when the remote ASP is available.
Probable Cause:This is sent by the peer SCCP layer when one of its apps (subsystems), such as the HLR, is out of commission.
Action to be Taken:Receiving node needs to update the translation tables so that traffic can be directed to a backup system if available.
Condition Clear Alarm:A starSCCPSspClear notification is generated when this condition is cleared.
SGSN has received a Radio Network Controller reset event. SGSN will clean up all the lu connections.
Important: This event is not generated for RNC Reset the first time the system boots up.Probable Cause:Remote GSN is down.
Condition Clear Alarm:A starSGSNGtpcPathFailureClear alarm is generated when the GSN becomes reachable.
Probable Cause:Remote GSN is down.
Action to be Taken:Check if peer RNC or GSN is up.
Condition Clear Alarm:A starSGSNGtpuPathFailureClear message is generated when the remote GSN becomes available again.
Probable Cause: Physical link is down, Layer 2 SSCOP/MTP2 is down, or link was deactivated by operator.
Condition Clear Alarm: A starMTP3LinkInService message is generated when the link is restored.
Probable Cause:All links in linkset are down or linkset was deactivated by operator.
Condition Clear Alarm:A starMTP3LinkSetAvailable message is generated when the previously down linkset is restored.
Probable Cause:Peer is down, or network is down, or the endpoint configuration is incorrect at our end.
Condition Clear Alarm:A starSCTPAssociationEstablished message is sent when a previously failed association is restored.
Probable Cause:Peer is down. Network to the remote server is down. The endpoint configuration is incorrect at our end.
Condition Clear Alarm:A starSCTPPathUp notification is generated when the path is restored.
Probable Cause:Network is down. Port is disconnected.
Condition Clear Alarm:A starPortUp notification is generated when the port is restored.
Probable Cause:The base station has failed or the network has connectivity problems.
Action to be Taken:If the outage was unplanned, reboot the base station and verify network connectivity.
Condition Clear Alarm:A starBSReachable notification is generated when the base station is reconnected.
Probable Cause:All links within the linkset become unavailable. Remote peer is down.
Condition Clear Alarm:A starMTP3PCAvailable message is generated when the route to the point code is reestablished.
Probable Cause:All MTP3 and M3UA routes to the point code are unavailable.
Condition Clear Alarm:A starSS7PCAvailable message is generated when the route is reestablished.
Probable Cause:One of the M3UA or MTP3 routes is back up.
Action to be Taken:No action required.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the ASNPC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the ASNPC service is operational.
Probable Cause:Connections have been torn down due to an error in the Capability Exchange Answer received from the peer.
Probable Cause:Network connectivity problem.
Action to be Taken:Verify standby system is operational and check the network connections are up.
Clear Condition:A starSRPConnUp notification is generated when condition is cleared.
Probable Cause: The Diameter peer has failed, or a network connectivity prevents reaching the peer.
Condition Clear Alarm: A starDiameterPeerUp notification will be generated when the peer is up.
Probable Cause:The IPMS server has failed, or a network connectivity issue prevents reaching the server.
Condition Clear Alarm:A starIPMSServerReachable notification will be generated when the server becomes reachable.
Action to be Taken:A new certificate should be created and configured on the system.
Action to be Taken:A new certificate should be created and configured on the system.
Condition Clear Alarm:A starCertValid notification is sent when a new, valid, certificate is configured.
Condition Clear Alarm:This condition is cleared by a starSDHSectionUp notification
Condition Clear Alarm:This condition is cleared by a starSDHLopDown notification
Probable Cause:All the routes (both M3UA and MTP3) to this point code have become congested.
Condition Clear Alarm: A starSS7PCCongestionCleared notification will be generated when the congestion gets cleared for any one of the routes.
Action to be Taken:No action required
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the PHS-GW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the PHS-GW service is operational
Condition Clear Alarm: A starPHSGWServiceStart notification will be generated when the service is restarted
Action to be Taken:No action required
Action to be Taken:If the GPRS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the GPRS service is operational.
Condition Clear Alarm:A starGPRSServiceStart notification will be generated when the service is restarted
Possible Cause:The last NSVC (Network Service virtual circuit in the NSE is down.
Condition Clear Alarm:A starGPRSNseUp will be generated when at least one NSVC in the NSE comes up.
Condition Clear Alarm:A starGPRSNseUp notification is generated only when a previous starGPRSNseDown has been generated.
Probable Cause:NS_ALIVE heartbeat messages sent from the Serving GPRS Support Node (SGSN) were not acknowledged by the Base Station Subsystem (BSS) for a configured number of maximum retries. This trap is generated only when an NSVC goes down due to reasons other than physical port failure. A separate trap is generated for a physical port failure event.
Condition Clear Alarm:A starGPRSNsvcUp will be generated when the NSVC is restored.
Probable Cause:All Network Service Entity Virtual Circuits (NSVC) associated with this BVC are down.
Condition Clear Alarm:A starGPRSBvcUp will be generated when the BVC is available.
Probable Cause: At least one NSVC associated with the BVC becomes available. A starGPRSBvcUp is generated only when a previous starGPRSBvcDown has been generated.
Condition Clear Alarm: This condition is cleared by a starSDHTugUp notification
Action to be Taken:No action required
Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration
Action to be Taken:If the PHS-PC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the PHS-PC service is operational.
Condition Clear Alarm:A starPHSPCServiceStart notification will be generated when the service is restarted.
Probable Cause:No Stream Control Transmission Protocol (SCTP) acknowledgement from peer server due to packet loss, or an acknowledgement with zero window size.
Condition Clear Alarm:A starM3UAPSPCongestionCleared notification will be generated when the congestion queue size goes below the threshold limit.
Probable Cause:A hardware failure on the device, or a hardware failure on the card to which the device is attached.
Action to be Taken:Replace the card.
Condition Clear Alarm:A starCardRemoved notification will be generated when the card is removed from the chassis.
Probable Cause:Hardware failure(s) on the devices within the raid array; or hardware failure(s) on the card(s) to which the devices are attached; or the removal of the cards containing devices in the array; or operator action which disabled the raid array.
Condition Clear Alarm:A starRaidStarted notification will be generated when the raid array is online.
Probable Cause:Hardware failure(s) on the devices within the raid array; hardware failure(s) on the card(s) to which the devices are attached; the removal of the cards containing devices in the array; operator action which disabled the raid array.
Condition Clear Alarm:A starRaidRecovered notification will be generated when the raid array is fully recovered.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the PGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the PGW service is operational.
Condition Clear Alarm:A starPGWServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the SGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the SGW service is operational.
Condition Clear Alarm:A starSGWServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the configuration.
Action to be Taken:If the EGTP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the EGTP service is operational.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken:If the LMA service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the LMA service is operational.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken:If the MAG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the MAG service is operational.
Condition Clear Alarm:A starMAGServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required.
Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources (packet processing cards) to support the running configuration.
Action to be Taken:If the MME service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the MME service is operational.
Condition Clear Alarm: A starMMEServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (packet processing cards) to support the running configuration.
Action to be Taken:If the HSGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the HSGW service is operational.
Conditio Clear Alarm:A starHSGWServiceStart notification will be generated when the service is restarted.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the FNG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running on the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the FNG service is operational.
Condition Clear Alarm:A starFNGServiceStart notification will be generated when the service is restarted.
Action to be Taken: No action required.
Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the PDG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the PDG service is operational.
Condition Clear Alarm:A starPDGServiceStart notification will be generated when the service is restarted.
Condition Clear Alarm:This condition is cleared by a starDynPkgLoadErrorClear notification.
Probable Cause:Remote peer MME or SGW or PGW is down.
Condition Clear Alarm:A StarEgtpcPathFailureClear notification will be generated when the control path to the remote peer MME or SGW or PGW becomes available.
Probable Cause:This is the result of an operator-configured congestion threshold being reached for CSCF Service at Session Manager. This can be due to high usage of the resource being monitored which indicates that the IMG is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds.
Actions to be Taken:Verify that the congestion thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
Condition Clear Alarm:A starCscfSessResourceCongestionClear notification is sent when there are no congestion conditions for CSCF service in that Session Manager instance.
Condition Clear Alarm:A starOSPFv3NeighborFull notification is only sent for neighbors which had previously been declared down via a starOSPFv3NeighborDown notification.
Probable Cause:Remote EPC node is down.
Condition Clear Alarm:A starEgtpuPathFailureClear notification will be generated when the data path towards the peer node is available.
GTPP Storage Server is experiencing CDR Loss greater than the configured threshold value at the GSS.
Action to be Taken: No action required
Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of packet processing card resources to support the running configuration
Action to be Taken: If the HNB GW service shutdown was not planned, examine the ad min logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure
Clear Condition: Verify that the HNB GW service is operational
Condition Clear Alarm: A starHNBGWServiceStart notification will be generated when the service is restarted.
Action to be Taken: No action required. If the reboot was not scheduled the admin logs can be examined to determine who invoked the reboot operation.
Action to be Taken: A new license should be created and configured on the system before the grace period is over.
Action to be Taken: A new license should be created and configured on the system.
Action to be Taken: No action required
Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken: If the PCC-Policy service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the PCC-Policy service is operational.
Condition Clear Alarm:A starPCCPolicyServiceStart notification will be generated when the service is restarted.
Action to be Taken: No action required
Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken: If the PCC-Quota service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the PCC-Quota service is operational.
Condition Clear Alarm: A starPCCQuotaServiceStart notification will be generated when the service is restarted
Action to be Taken: No action required
Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken: If the PCC-AF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the PCC-AF service is operational.
Condition Clear Alarm: A starPCCAFServiceStart notification will be generated when the service is restarted.
Probable Cause:The SPR server is down, or there is a network issue preventing communication with the SPR server.
Action to be Taken:Restore the SPR server to an operational status; Verify that the SPR server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems.
Clear Condition:Verify that communication to the SPR authentication server has been restored.
Condition Clear Alarm:When this condition clears a starSPRServerReachable notification will be generated.
Action to be Taken:No Action Required.
Action to be Taken: No action required.
Probable Cause: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the GS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Action to be Taken: No action required
Probable Cause:: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the IUPS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the IUPS service is operational.
Action to be Taken:No action required.
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken:If the SGTP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the SGTP service is operational.
Action to be Taken:No action required.
Probable Cause: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of hardware resources to support the running configuration.
Action to be Taken: If the EPDG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition: Verify that the EPDG service is operational.
Condition Clear Alarm: A starEPDGServiceStart notification will be generated when the service is restarted.
Action to be Taken: No action required
Probable Cause:This is typically caused by operator intervention. In unusual cases it can be caused by the loss of packet processing card resources to support the running configuration.
Action to be Taken:If the SGS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured packet processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Clear Condition:Verify that the SGS service is operational.
Condition Clear Alarm:A starSGSServiceStart notification will be generated when the service is restarted.
Action to be Taken:If the shutdown of the eNodeB was not planned, determine the health/status of the eNodeB. If available, verify the health of the network between the two elements.
Clear Condition:The condition is cleared when the S1 Association is reestablished.
Action to be Taken:No action required
Probable Cause: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of packet processing card resources to support the running configuration.
Action to be Taken: If the BNG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured processing cards are present and running in the system. Check the crash logs for an indication of a software failure.
Condition Clear Alarm: A starBNGServiceStart notification will be generated when the service is restarted.
Action to be Taken:If the shutdown of the eNodeB was not planned, determine the health/status of the eNodeB. If available, verify the health of the network between the two elements.
Clear Condition:The condition is cleared when the S1 Association is reestablished.
Condition Clear Alarm:A starMMES1AssocEstab notification will be generated when the S1 association is re-established
Problem Cause:The MVG peer has failed, or a network connectivity prevents reaching the peer.
Condition Clear Alarm:A starMVGPeerUp notification will be generated when the peer is up.
Probable Cause:The Event Notification server on SPR is down or the IP-address/port configuration does not match with the server.
Actions to be Taken:Check the Event Notification server on SPR and ensure it is running. Ensure that IP-address port combination on IPCF match the server side configurations
Condition Clear Alarm:When this condition clears, a starNtfyIntfPeerReachable notification will be generated.
Action to be Taken: No action required.
Action to be Taken: No Action Required.
Probable Cause: The IPSec Node peer has failed, or a network connectivity prevents reaching the peer.
Condition Clear Alarm: A starIPSecNodePeerUp notification will be generated when the peer is up.
Action to be Taken: No action required.
Probable Cause:A command was issued which resulted in a new user being added to the local user database. If this was not a planned action then further investigation is advised.
Probable Cause:A command was issued which resulted in an existing user being removed from the local user database. If this was not a planned action then further investigation is advised.
Probable Cause:A command was issued which resulted in an existing user's privileges being modified. If this was not a planned action then further investigation is advised.
Probable Cause:A command was issued which resulted in a user's access to the operating system shell. If this was not a planned action then further investigation is advised.
Probable Cause:A command was issued which resulted in a user entering the CLI test command mode. The test command mode is only intended for maintenance and diagnostic activity and access could result in major service disruptions. If this was not a planned action the user should exit from test mode.
Probable Cause:A command was issued which resulted in a user modifying the set of licensed features. This ability was only intended for maintenance and diagnostic activityand could result in major service disruptions. If this action was not intentional, the user should restore the original license feature set.
Probable Cause:A command was configured which resulted in users having access to the specific test commands which may have been previously unavailable. If this action was not intentional, the user should disable access to the hidden test commands.
Probable Cause:A command was configured which resulted in users no longer having access to specific test commands which may have been previously available. If this action was not intentional, the user should re-enable access to the hidden test commands.
Action to be Taken:If the shutdown of the eNodeB was not planned, determine the health/status of the eNodeB. If available, verify the health of the network between the two elements.
Condition Clear Alarm:A starMMES1PathEstab notification will be generated when the S1 path is re-established.
Action to be Taken: None required. Alarm is cleared when the IPv6 entries go below the Lower Water Mark configured.
Problem Cause: The IPSec Node peer has failed, or a network connectivity problem exists.
Condition Clear Alarm: A starIPSecNodeIpv6PeerUp notification will be generated when the peer is up.
Action to be Taken: No action required. The cause for the LAG down should be investigated.
Action to be Taken: No action required.
